- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Re: incorrect domain suffix search list W2K3 and P...
ProLiant Servers - Netservers
1755655
Members
2684
Online
108837
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 08:29 PM
тАО12-04-2006 08:29 PM
incorrect domain suffix search list W2K3 and PSP7.60A
Just installed new server with W2K3 and PSP 7.60A
All seems fine but system cannot contact WSUS-server (and any other servers in same DNS-domain) by shortname.
Seems like default-domain suffix is not used when doing DNS-queries or domain-suffix is faulty (ip-adresses instead of names!).
Any tips how to troubleshoot this?
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : nlw-db10
Primary Dns Suffix . . . . . . . : naaldwijk.intranet.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 10.1.1.91
10.1.1.92
C:\>nslookup
Default Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
> nlw-dc02
Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
*** nlw-dc02.naaldwijk.intranet.int can't find nlw-dc02: Non-existent domain
> nlw-dc02.naaldwijk.intranet.int
Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
Name: nlw-dc01.naaldwijk.intranet.int
Address: 10.1.1.92
>
All seems fine but system cannot contact WSUS-server (and any other servers in same DNS-domain) by shortname.
Seems like default-domain suffix is not used when doing DNS-queries or domain-suffix is faulty (ip-adresses instead of names!).
Any tips how to troubleshoot this?
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : nlw-db10
Primary Dns Suffix . . . . . . . : naaldwijk.intranet.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : 10.1.1.91
10.1.1.92
C:\>nslookup
Default Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
> nlw-dc02
Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
*** nlw-dc02.naaldwijk.intranet.int can't find nlw-dc02: Non-existent domain
> nlw-dc02.naaldwijk.intranet.int
Server: nlw-dc02.naaldwijk.intranet.int
Address: 10.1.1.92
Name: nlw-dc01.naaldwijk.intranet.int
Address: 10.1.1.92
>
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2007 06:07 AM
тАО01-11-2007 06:07 AM
Re: incorrect domain suffix search list W2K3 and PSP7.60A
Make sure you have your TCP/IP stack pointed at a functioning DNS server, either a private or a public IP should work fine. I just had this situation on a new Proliant install and I pointed my DNS at my private Gateway IP address (192.168.0.1) and it worked fine.
To test you can open up a cmd window and try to ping a known functioning site like www.novell.com. If that doesn't work, try to ping your dns server(s) on the public side of your firewall. If that doesn't work try pinging your private gateway address.
Try taking out your domain suffix if the above doesn't get you working.
To test you can open up a cmd window and try to ping a known functioning site like www.novell.com. If that doesn't work, try to ping your dns server(s) on the public side of your firewall. If that doesn't work try pinging your private gateway address.
Try taking out your domain suffix if the above doesn't get you working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2007 11:00 PM
тАО03-26-2007 11:00 PM
Re: incorrect domain suffix search list W2K3 and PSP7.60A
Timothy, i just recently saw your answer.
Yes we do have a working nameserver.
and i can resolve names using FQDN.
and it worked before applying the PSP.
But after installation of the PSP my dns-suffix searchlist is changed ! instead of attaching my own dns-suffix (naaldwijk.intranet.int) suddenly it attached the ip-adresses of the dns-servers instead of the domain-names.
Yes we do have a working nameserver.
and i can resolve names using FQDN.
and it worked before applying the PSP.
But after installation of the PSP my dns-suffix searchlist is changed ! instead of attaching my own dns-suffix (naaldwijk.intranet.int) suddenly it attached the ip-adresses of the dns-servers instead of the domain-names.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP