I am hoping someone can help me on this. Apologies for merely being dangerous with DNS.
I have two DNS servers running on Server 2008 Standard and they have resolved names just fine until recently. We now find that subdomains, e.g., reports.servername, will not resolve unless from XP or Windows 2003. When I ping from an internal Win 2008 Server or Win 7 machine, I get a "request timed out" response from an external IP address. However, I can ping the parent server name, e.g., servername from 2008 ro Win7.
The above is true for other servers (reports.stagingservername) as well as other subdomains (services.servername or services.stagingservername). I can ping & receive from XP/2003 but not 7/2008.
I notice that it is not resolving the FQDN. If I ping reports.servername.domainname.local I can get a proper reply from 7/2008 machines. Now, I have tried manually specifying in my adapter settings to append domainname.local suffix to no avail. Even if that did work, it would make no sense being that no mass local changes (GPO changes, for example) have been made recently. I am not sure about changes on the DNS servers, however.
What makes this more interesting is that I cannot even properly resolve from either of my own DNS servers (2008). But I can do so just fine from XP or 2003 machines using those very DNS servers as nameservers (even after flushing the cache on the XP or 2003 box).
Does anyone have any idea why 2003-based machines would behave differently in resolving than the later 2008/7 machines? If not, is there a way around this that anyone can suggest?
Thanks in advance.
I have two DNS servers running on Server 2008 Standard and they have resolved names just fine until recently. We now find that subdomains, e.g., reports.servername, will not resolve unless from XP or Windows 2003. When I ping from an internal Win 2008 Server or Win 7 machine, I get a "request timed out" response from an external IP address. However, I can ping the parent server name, e.g., servername from 2008 ro Win7.
The above is true for other servers (reports.stagingservername) as well as other subdomains (services.servername or services.stagingservername). I can ping & receive from XP/2003 but not 7/2008.
I notice that it is not resolving the FQDN. If I ping reports.servername.domainname.local I can get a proper reply from 7/2008 machines. Now, I have tried manually specifying in my adapter settings to append domainname.local suffix to no avail. Even if that did work, it would make no sense being that no mass local changes (GPO changes, for example) have been made recently. I am not sure about changes on the DNS servers, however.
What makes this more interesting is that I cannot even properly resolve from either of my own DNS servers (2008). But I can do so just fine from XP or 2003 machines using those very DNS servers as nameservers (even after flushing the cache on the XP or 2003 box).
Does anyone have any idea why 2003-based machines would behave differently in resolving than the later 2008/7 machines? If not, is there a way around this that anyone can suggest?
Thanks in advance.