dns suffix issue – please help!

25 pts.
Tags:
Active Directory
Active Directory 2003
DNS
DNS Suffix
Windows
Windows Server 2003
Hello, We are currently restructuring our company's DNS which is all server 2003. Each of our sites are being added into dns so they will have their own zones. What I noticed is that as soon as I put, say, miami.company.local as the primary domain suffix on a client, that machine is no longer allowed to browse the root company.local in network places=>all networks=>microsoft=>company strangely enough it seems to work when browsing this path on a server. It just doesn't work when changing the dns suffix on a client machine. The new suffix has been added to msds-alloweddnssuffixes attribute in root schema on the server. This should then allow clients to use that suffix... Any ideas as to why this might be? Thanks, Taz
ASKED: February 10, 2009  10:12 PM
UPDATED: February 12, 2009  9:42 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Whats the error message you are receiving in the eventlog on the client? Can you post that?? Whats the OS on the client??

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Pjb0222
    Review the domain suffix search order on your system or handed out through DHCP. Which client OS? Windows XP will devolve DNS lookups by default while Windows Vista does not (requires reg hack). My guess is that you do not have a search order set to allow resolution into the other domains. To test this, use a non-FQDN (short name) lookup and then a FQDN lookup of a system in another domain. - first: nslookup systemname - second: nslookup systemname.subdomain.domain This will give information on how things are working and clues on where to start troubleshooting.
    3,310 pointsBadges:
    report
  • Taz72
    Hi, Thanks for your replies. It turned out the CheckPoint Secure Client vpn software was bound to the NIC's of the affected machines, hence it was blocking access mentioned above. As soon as this was unchecked from tcp/ip stack, the problem seems to have been solved. Thanks, Taz
    25 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following