• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 807
  • Last Modified:

DNS issus

We are experiencing some strange DNS issues with our network. We have 2008 Sever with Exchange 2010 running as a DC, GC, DNS and a Server 2003 running as a DC, GC, DNS. We occasionally get ‘Delivery is delayed to these recipients or groups:’ messages on emails and now we are getting ‘Delivery has failed to these recipients or groups’

To add to this some of the domain PC’s are unable to browse network shares \\winserver8 as they seem to be unable to resolve DNS but also if you enter the IP address of the share \\10.0.254.8 this still does not work. Are these problems related?


How can I resolve this problem?
0
Fubschuk
Asked:
Fubschuk
  • 4
  • 3
  • 2
  • +1
1 Solution
 
Randy DownsOWNERCommented:
yeah I'd say that unable to browse & unable to deliver email are realated. Sounds like you are dropping off the network.
0
 
Patmac951Commented:
From the command prompt on the servers can you possibly run this command: c:>DCDIAG /TEST:DNS

Then post the results?

If you are unable to access network devices via IP address this is not a DNS issue.  DNS is used to resolve computer names back to IP addresses, if you are unable to access the devices via IP address you are having another network issue that is not DNS related.
0
 
Patmac951Commented:
Secondly for the computers that are not able to communicate via IP addresses can you successfully ping the Domain controllers from these workstations?  For testing purposes have you tried to remove the computer from the domain to a workgroup, reboot the computer then try join the domain again?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
NetfloCommented:
Fubschuk,

1. Can you please ensure that the local DNS servers configured on both servers are not set to external DNS or ISP DNS server, these need to be configured via forwarders in DNS.

2. If you review the DNS logs in Event Viewer does it point out any issues?

3. You can also enable the "use the external dns lookup settings on the transport" setting on your Exchange 2010 Send Connector which routes emails to the internet.
Please see the following article to enable this http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.connectivity/2009-02/msg00011.html

Hope this helps, let us know how you get on.
0
 
FubschukAuthor Commented:
Results from DCDIAG /TEST:DNS attached.

 DNS8-1.txt
 DNS13-1.txt
The DNS tests passed

I can ping the IP address of the machines on the network. I have removed one of the machines from the domain, then tried to re-connect but get the message the domain controller could not be found.
I'm guessing that because I can't browse any share from this machine

The DNS event logs on both machines have no errors.
Winserver8 does have a lot of information events with...
The DNS server encountered a bad packet from nn.nn.nn.nn.  Packet processing leads beyond packet length. The event data contains the DNS packet
0
 
NetfloCommented:
From your attached logs, it looks like your server is querying the root server, have you got DNS forwarders configured?

Go to DNS -> Right click on your server -> Properties -> Forwarders tab -> If the following list is empty, press Edit and type in either your ISPs DNS servers or Google DNS servers [8.8.8.8 and 8.8.4.4], the latter may be a preferred option if you have multiple ISP providers or just want a more resilient DNS network.

Also have you got a reverse DNS zone created in your DNS for  your local network, bearing in mind that it is not created by default.

Go to DNS -> Expand your server -> Right click on Reverse Lookup Zones -> New Zone -> Next -> Primary Zone -> Next -> To all DNS servers running on domain controllers in this domain -> Next -> IPv4 reverse lookup zone -> Next -> Network ID (e.g. 192.168.1) -> Next -> Allow only secure dynamic updates -> Finish

Let us know how you get on.
0
 
FubschukAuthor Commented:
I have made the changes as neither DNS had forwarders configured so added Googles DNS, and the reverselookup for my network.

I will see how this works over the weekend.
0
 
NetfloCommented:
One final point, can you please ensure the following is done, as listed previously:

3. You can also enable the "use the external dns lookup settings on the transport" setting on your Exchange 2010 Send Connector which routes emails to the internet.
Please see the following article to enable this http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.connectivity/2009-02/msg00011.html
0
 
FubschukAuthor Commented:
The problem with the PC’s not being able to connect or see files shares was a red herring. I fixed that myself there was a driver problem caused by a windows update on some of the machines.

The Email retries and fails were the problem solved here.
0
 
NetfloCommented:
Glad to hear everything is okay.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now