DNS Problems

I suspect that DNS issues are causing me to have email messages arrive hours
or even a day later. I ran dcdiag /test:dns and received the output below.
I am able to successfully query other domains, and everything appears to be
functioning fine. I'm not sure why the test is failing or what caused it.
Without the sometimes slow mail delivery, I would not even know there was a
problem. Any help in troubleshooting the problem would be greatly appreciated.

Thanks.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SDSERVER
Starting test: Connectivity
......................... SDSERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SDSERVER

DNS Tests are running and not hung. Please wait a few minutes...

Running partition tests on : SDSR

Running partition tests on : Schema

Running partition tests on : Configuration

Running enterprise tests on : Shiprepair.com
Starting test: DNS
Test results for domain controllers:

DC: sdserver.SDSR.Shiprepair.com
Domain: SDSR.Shiprepair.com


TEST: Basic (Basc)
Warning: adapter [00000005] HP NC7760 Gigabit Server
Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)
Error: all DNS servers are invalid

TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the
network adapters

Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 172.20.100.10 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.100.10

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

__________________________________________________ ______________
Domain: SDSR.Shiprepair.com
sdserver PASS FAIL n/a n/a n/a FAIL
n/a

......................... Shiprepair.com failed test DNS

--
DLove

Are you using ISP DNS? I would create an internal DNS instead of using ISP DNS. This case study may help too,

Some sent emails are dropped occasionally Then they give us two new DNS and we re-assign these two DNS IP addresses in the DNS forwarders. That fixes the problem. Related Topics. Exchange Case ...
www.chicagotech.net/exchange/dropemail.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"dlove106" <(E-Mail Removed)> wrote in message news:391243CF-6697-4C2D-B63F-(E-Mail Removed)...
I suspect that DNS issues are causing me to have email messages arrive hours
or even a day later. I ran dcdiag /test:dns and received the output below.
I am able to successfully query other domains, and everything appears to be
functioning fine. I'm not sure why the test is failing or what caused it.
Without the sometimes slow mail delivery, I would not even know there was a
problem. Any help in troubleshooting the problem would be greatly appreciated.

Thanks.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SDSERVER
Starting test: Connectivity
......................... SDSERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SDSERVER

DNS Tests are running and not hung. Please wait a few minutes...

Running partition tests on : SDSR

Running partition tests on : Schema

Running partition tests on : Configuration

Running enterprise tests on : Shiprepair.com
Starting test: DNS
Test results for domain controllers:

DC: sdserver.SDSR.Shiprepair.com
Domain: SDSR.Shiprepair.com


TEST: Basic (Basc)
Warning: adapter [00000005] HP NC7760 Gigabit Server
Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)
Error: all DNS servers are invalid

TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the
network adapters

Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 172.20.100.10 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.100.10

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

__________________________________________________ ______________
Domain: SDSR.Shiprepair.com
sdserver PASS FAIL n/a n/a n/a FAIL
n/a

......................... Shiprepair.com failed test DNS

--
DLove

Thank you for your response. I will go over the case study in the morning
and let you know the results. I am using internal DNS with my ISP as a
forwarder.
--
DLove


"Robert L [MS-MVP]" wrote:

> Are you using ISP DNS? I would create an internal DNS instead of using ISP DNS. This case study may help too,
>
> Some sent emails are dropped occasionally Then they give us two new DNS and we re-assign these two DNS IP addresses in the DNS forwarders. That fixes the problem. Related Topics. Exchange Case ...
> www.chicagotech.net/exchange/dropemail.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "dlove106" <(E-Mail Removed)> wrote in message news:391243CF-6697-4C2D-B63F-(E-Mail Removed)...
> I suspect that DNS issues are causing me to have email messages arrive hours
> or even a day later. I ran dcdiag /test:dns and received the output below.
> I am able to successfully query other domains, and everything appears to be
> functioning fine. I'm not sure why the test is failing or what caused it.
> Without the sometimes slow mail delivery, I would not even know there was a
> problem. Any help in troubleshooting the problem would be greatly appreciated.
>
> Thanks.
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\SDSERVER
> Starting test: Connectivity
> ......................... SDSERVER passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SDSERVER
>
> DNS Tests are running and not hung. Please wait a few minutes...
>
> Running partition tests on : SDSR
>
> Running partition tests on : Schema
>
> Running partition tests on : Configuration
>
> Running enterprise tests on : Shiprepair.com
> Starting test: DNS
> Test results for domain controllers:
>
> DC: sdserver.SDSR.Shiprepair.com
> Domain: SDSR.Shiprepair.com
>
>
> TEST: Basic (Basc)
> Warning: adapter [00000005] HP NC7760 Gigabit Server
> Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)
> Error: all DNS servers are invalid
>
> TEST: Records registration (RReg)
> Error: Record registrations cannot be found for all the
> network adapters
>
> Summary of test results for DNS servers used by the above domain
> controllers:
>
> DNS server: 172.20.100.10 (<name unavailable>)
> 1 test failure on this DNS server
> This is not a valid DNS server. PTR record query for the
> 1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.100.10
>
> Summary of DNS test results:
>
> Auth Basc Forw Del Dyn RReg
> Ext
>
> __________________________________________________ ______________
> Domain: SDSR.Shiprepair.com
> sdserver PASS FAIL n/a n/a n/a FAIL
> n/a
>
> ......................... Shiprepair.com failed test DNS
>
> --
> DLove

Robert, again thanks for the case study, however, it was not much help. I am
still stuck in the "DNS Black Hole". From the output listed in my original
post, can you gather any reason why the tests fail? Any specific
troubleshooting steps to take in working towards a resolution. I also posted
this same info in the DNS forum.

Thanks.
--
DLove


"Robert L [MS-MVP]" wrote:

> Are you using ISP DNS? I would create an internal DNS instead of using ISP DNS. This case study may help too,
>
> Some sent emails are dropped occasionally Then they give us two new DNS and we re-assign these two DNS IP addresses in the DNS forwarders. That fixes the problem. Related Topics. Exchange Case ...
> www.chicagotech.net/exchange/dropemail.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "dlove106" <(E-Mail Removed)> wrote in message news:391243CF-6697-4C2D-B63F-(E-Mail Removed)...
> I suspect that DNS issues are causing me to have email messages arrive hours
> or even a day later. I ran dcdiag /test:dns and received the output below.
> I am able to successfully query other domains, and everything appears to be
> functioning fine. I'm not sure why the test is failing or what caused it.
> Without the sometimes slow mail delivery, I would not even know there was a
> problem. Any help in troubleshooting the problem would be greatly appreciated.
>
> Thanks.
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: Default-First-Site-Name\SDSERVER
> Starting test: Connectivity
> ......................... SDSERVER passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SDSERVER
>
> DNS Tests are running and not hung. Please wait a few minutes...
>
> Running partition tests on : SDSR
>
> Running partition tests on : Schema
>
> Running partition tests on : Configuration
>
> Running enterprise tests on : Shiprepair.com
> Starting test: DNS
> Test results for domain controllers:
>
> DC: sdserver.SDSR.Shiprepair.com
> Domain: SDSR.Shiprepair.com
>
>
> TEST: Basic (Basc)
> Warning: adapter [00000005] HP NC7760 Gigabit Server
> Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)
> Error: all DNS servers are invalid
>
> TEST: Records registration (RReg)
> Error: Record registrations cannot be found for all the
> network adapters
>
> Summary of test results for DNS servers used by the above domain
> controllers:
>
> DNS server: 172.20.100.10 (<name unavailable>)
> 1 test failure on this DNS server
> This is not a valid DNS server. PTR record query for the
> 1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.100.10
>
> Summary of DNS test results:
>
> Auth Basc Forw Del Dyn RReg
> Ext
>
> __________________________________________________ ______________
> Domain: SDSR.Shiprepair.com
> sdserver PASS FAIL n/a n/a n/a FAIL
> n/a
>
> ......................... Shiprepair.com failed test DNS
>
> --
> DLove

In news:391243CF-6697-4C2D-B63F-(E-Mail Removed),
dlove106 <(E-Mail Removed)> stated, which I commented on below:
> I suspect that DNS issues are causing me to have email messages
> arrive hours or even a day later. I ran dcdiag /test:dns and
> received the output below.
> I am able to successfully query other domains, and everything appears
> to be functioning fine. I'm not sure why the test is failing or what
> caused it. Without the sometimes slow mail delivery, I would not even
> know there was a problem. Any help in troubleshooting the problem
> would be greatly appreciated.
>
> Thanks.

<smnipped>

One part of the error states:

"Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)"

What is that IP address? Is that one of yours?

Any errors in the Event logs? (If so, post the Event ID# and Source please).

I wouldn't say that DNS is causing failure to receive mail since that
function is performed by the sending email server sending you mail. As far
as Active Directory, this error can cause numerous other issues. Let's try
to figure out what's causing this. DNS is the basis of AD functionality, and
if you are getting this error in a DCDIAG, it's not looking good.

Can you also post an ipconfig /all from this DC (unedited please). That will
give us a great start to analyze the DC's configuration.

By chance did you also post this in the DNS groups? I usually post in there
and in the AD group, but didn't see your name. If not, for now, let;s keep
the post here and we'll try to help from here for now.


--
Ace
Innovative IT Concepts, Inc
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

--
DLove


"Ace Fekay [MVP]" wrote:

> In news:391243CF-6697-4C2D-B63F-(E-Mail Removed),
> dlove106 <(E-Mail Removed)> stated, which I commented on below:
> > I suspect that DNS issues are causing me to have email messages
> > arrive hours or even a day later. I ran dcdiag /test:dns and
> > received the output below.
> > I am able to successfully query other domains, and everything appears
> > to be functioning fine. I'm not sure why the test is failing or what
> > caused it. Without the sometimes slow mail delivery, I would not even
> > know there was a problem. Any help in troubleshooting the problem
> > would be greatly appreciated.
> >
> > Thanks.
>
> <smnipped>
>
> One part of the error states:
>
> "Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)"
>
> What is that IP address? Is that one of yours?

This IP belongs to my DC which is the DNS server.
>
> Any errors in the Event logs? (If so, post the Event ID# and Source please).

DNS Log -
Source: DNS
Event ID: 7062
Description: The DNS server encountered a packet addressed to itself on IP
address 172.20.100.10. The packet is for the DNS name
"1.0.0.127.in-addr.arpa.". The
packet will be discarded. This condition usually indicates a configuration
error.

System Log -
Source: DCOM
Event ID: 10009
Description: DCOM was unable to communicate with the computer 63.210.161.5
using any of the configured protocols. (This is the DNS address of my ISP. I
listed this error although the IP changes. Sometimes it lists my internal
5.5 mail server, other times a remote server. Not sure if this is normal
event that will occur for a few moments).


>
> I wouldn't say that DNS is causing failure to receive mail since that
> function is performed by the sending email server sending you mail. As far
> as Active Directory, this error can cause numerous other issues. Let's try
> to figure out what's causing this. DNS is the basis of AD functionality, and
> if you are getting this error in a DCDIAG, it's not looking good.

I was thinking DNS because Mail is occassionally slow. Meaning that it may
arrive hours or days late. This includes tests I perform each morning from
my personal account to my work address.
>
> Can you also post an ipconfig /all from this DC (unedited please). That will
> give us a great start to analyze the DC's configuration.

Windows IP Configuration

Host Name . . . . . . . . . . . . : sddcsrv03
Primary Dns Suffix . . . . . . . : Shiprepair.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Shiprepair.com

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-B0-D0-B2-3E-A9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.20.100.10
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.20.0.2
DNS Servers . . . . . . . . . . . : 172.20.100.10
Primary WINS Server . . . . . . . : 172.20.0.30

>
> By chance did you also post this in the DNS groups? I usually post in there
> and in the AD group, but didn't see your name. If not, for now, let;s keep
> the post here and we'll try to help from here for now.

I did post this in the DNS group. I did not find anything to help me at the
moment. I may have changed the Subject to "DCDIAG" errors.

Thanks for your help.
>
>
> --
> Ace
> Innovative IT Concepts, Inc
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...
>
>
>

In news:4EC66F80-6BFF-407F-95EF-(E-Mail Removed),
dlove106 <(E-Mail Removed)> stated, which I commented on below:
>
>> In news:391243CF-6697-4C2D-B63F-(E-Mail Removed),
>> dlove106 <(E-Mail Removed)> stated, which I commented on
>> below:
>>> I suspect that DNS issues are causing me to have email messages
>>> arrive hours or even a day later. I ran dcdiag /test:dns and
>>> received the output below.
>>> I am able to successfully query other domains, and everything
>>> appears to be functioning fine. I'm not sure why the test is
>>> failing or what caused it. Without the sometimes slow mail
>>> delivery, I would not even know there was a problem. Any help in
>>> troubleshooting the problem would be greatly appreciated.
>>>
>>> Thanks.
>>
>> <smnipped>
>>
>> One part of the error states:
>>
>> "Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)"
>>
>> What is that IP address? Is that one of yours?
>
> This IP belongs to my DC which is the DNS server.
>>
>> Any errors in the Event logs? (If so, post the Event ID# and Source
>> please).
>
> DNS Log -
> Source: DNS
> Event ID: 7062
> Description: The DNS server encountered a packet addressed to itself
> on IP address 172.20.100.10. The packet is for the DNS name
> "1.0.0.127.in-addr.arpa.". The
> packet will be discarded. This condition usually indicates a
> configuration error.
>
> System Log -
> Source: DCOM
> Event ID: 10009
> Description: DCOM was unable to communicate with the computer
> 63.210.161.5 using any of the configured protocols. (This is the DNS
> address of my ISP. I listed this error although the IP changes.
> Sometimes it lists my internal
> 5.5 mail server, other times a remote server. Not sure if this is
> normal event that will occur for a few moments).
>
>
>>
>> I wouldn't say that DNS is causing failure to receive mail since that
>> function is performed by the sending email server sending you mail.
>> As far as Active Directory, this error can cause numerous other
>> issues. Let's try to figure out what's causing this. DNS is the
>> basis of AD functionality, and if you are getting this error in a
>> DCDIAG, it's not looking good.
>
> I was thinking DNS because Mail is occassionally slow. Meaning that
> it may arrive hours or days late. This includes tests I perform each
> morning from my personal account to my work address.
>>
>> Can you also post an ipconfig /all from this DC (unedited please).
>> That will give us a great start to analyze the DC's configuration.
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : sddcsrv03
> Primary Dns Suffix . . . . . . . : Shiprepair.com
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Shiprepair.com
>
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
> Ethernet Controller (3C905C-TX Compatible)
> Physical Address. . . . . . . . . : 00-B0-D0-B2-3E-A9
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 172.20.100.10
> Subnet Mask . . . . . . . . . . . : 255.255.0.0
> Default Gateway . . . . . . . . . : 172.20.0.2
> DNS Servers . . . . . . . . . . . : 172.20.100.10
> Primary WINS Server . . . . . . . : 172.20.0.30


Thanks for posting that info. Here's a few things I would do:

Configure a forwarder to only your ISP DNS using 63.210.161.5. If that
doesn't work, try 4.2.2.2. Should eliminate the 7062.

Configure a reverse zone for 172.20.x.x. Make sure a PTR gets registered for
the DC. (Should eliminate the DCOM error).

I don't know why it would list your internal Ex5.5 server. I am assuming ALL
machines are ONLY using 172.20.100.10 as their DNS address and no others.

As far as the 127.0.0.1 in the message, is any machine (especially the DCs)
configured to use 127.0.0.1 in it's IP properties, or anywhere else? If so,
change it to the actual IPaddress of the machine.

Ace

Sorry for not posting sooner, but was under the weather for a few days. I
seem to have solved the error by doing the following:

1. Adding a ptr record for the loopback address in the reverse lookup zone.
2. Having the DNS server point to the loopback address instead of hard
coding its own ip address for the preferred dns server. (Clients still point
to server ip address)

Thank you again for your response and help.
--
DLove


"Ace Fekay [MVP]" wrote:

> In news:4EC66F80-6BFF-407F-95EF-(E-Mail Removed),
> dlove106 <(E-Mail Removed)> stated, which I commented on below:
> >
> >> In news:391243CF-6697-4C2D-B63F-(E-Mail Removed),
> >> dlove106 <(E-Mail Removed)> stated, which I commented on
> >> below:
> >>> I suspect that DNS issues are causing me to have email messages
> >>> arrive hours or even a day later. I ran dcdiag /test:dns and
> >>> received the output below.
> >>> I am able to successfully query other domains, and everything
> >>> appears to be functioning fine. I'm not sure why the test is
> >>> failing or what caused it. Without the sometimes slow mail
> >>> delivery, I would not even know there was a problem. Any help in
> >>> troubleshooting the problem would be greatly appreciated.
> >>>
> >>> Thanks.
> >>
> >> <smnipped>
> >>
> >> One part of the error states:
> >>
> >> "Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)"
> >>
> >> What is that IP address? Is that one of yours?
> >
> > This IP belongs to my DC which is the DNS server.
> >>
> >> Any errors in the Event logs? (If so, post the Event ID# and Source
> >> please).
> >
> > DNS Log -
> > Source: DNS
> > Event ID: 7062
> > Description: The DNS server encountered a packet addressed to itself
> > on IP address 172.20.100.10. The packet is for the DNS name
> > "1.0.0.127.in-addr.arpa.". The
> > packet will be discarded. This condition usually indicates a
> > configuration error.
> >
> > System Log -
> > Source: DCOM
> > Event ID: 10009
> > Description: DCOM was unable to communicate with the computer
> > 63.210.161.5 using any of the configured protocols. (This is the DNS
> > address of my ISP. I listed this error although the IP changes.
> > Sometimes it lists my internal
> > 5.5 mail server, other times a remote server. Not sure if this is
> > normal event that will occur for a few moments).
> >
> >
> >>
> >> I wouldn't say that DNS is causing failure to receive mail since that
> >> function is performed by the sending email server sending you mail.
> >> As far as Active Directory, this error can cause numerous other
> >> issues. Let's try to figure out what's causing this. DNS is the
> >> basis of AD functionality, and if you are getting this error in a
> >> DCDIAG, it's not looking good.
> >
> > I was thinking DNS because Mail is occassionally slow. Meaning that
> > it may arrive hours or days late. This includes tests I perform each
> > morning from my personal account to my work address.
> >>
> >> Can you also post an ipconfig /all from this DC (unedited please).
> >> That will give us a great start to analyze the DC's configuration.
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : sddcsrv03
> > Primary Dns Suffix . . . . . . . : Shiprepair.com
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : Shiprepair.com
> >
> > Ethernet adapter Local Area Connection:
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
> > Ethernet Controller (3C905C-TX Compatible)
> > Physical Address. . . . . . . . . : 00-B0-D0-B2-3E-A9
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 172.20.100.10
> > Subnet Mask . . . . . . . . . . . : 255.255.0.0
> > Default Gateway . . . . . . . . . : 172.20.0.2
> > DNS Servers . . . . . . . . . . . : 172.20.100.10
> > Primary WINS Server . . . . . . . : 172.20.0.30
>
>
> Thanks for posting that info. Here's a few things I would do:
>
> Configure a forwarder to only your ISP DNS using 63.210.161.5. If that
> doesn't work, try 4.2.2.2. Should eliminate the 7062.
>
> Configure a reverse zone for 172.20.x.x. Make sure a PTR gets registered for
> the DC. (Should eliminate the DCOM error).
>
> I don't know why it would list your internal Ex5.5 server. I am assuming ALL
> machines are ONLY using 172.20.100.10 as their DNS address and no others.
>
> As far as the 127.0.0.1 in the message, is any machine (especially the DCs)
> configured to use 127.0.0.1 in it's IP properties, or anywhere else? If so,
> change it to the actual IPaddress of the machine.
>
> Ace
>
>
>

In news:4EF1F894-799F-4646-BC22-(E-Mail Removed),
dlove106 <(E-Mail Removed)> stated, which I commented on below:
> Sorry for not posting sooner, but was under the weather for a few
> days. I seem to have solved the error by doing the following:
>
> 1. Adding a ptr record for the loopback address in the reverse lookup
> zone.
> 2. Having the DNS server point to the loopback address instead of hard
> coding its own ip address for the preferred dns server. (Clients
> still point to server ip address)
>
> Thank you again for your response and help.

Glad to be of help. As for #2, I would suggest to use the actual IP and NOT
the loopback.

Ace