DNS server encountered an invalid domain name....

[Gregg Hill]

Hello!

A client's event log is full of these errors on their Win2000 AD server:
"The DNS server encountered an invalid domain name in a packet from
206.13.29.12. The packet is rejected."

The 206.13.29.12 IP address is one of the two DNS servers for SBC, their T1
provider. Why would their server be getting these packets from SBC's DNS
server?

Gregg Hill

 

[Ace Fekay [MVP]]

In

Hello!

A client's event log is full of these errors on their Win2000 AD
server: "The DNS server encountered an invalid domain name in a
packet from 206.13.29.12. The packet is rejected."

The 206.13.29.12 IP address is one of the two DNS servers for SBC,
their T1 provider. Why would their server be getting these packets
from SBC's DNS server?

Gregg Hill

What is the exact Event ID #? 5504?
Are you using 206.13.29.12 in your machines' IP properties or is
206.13.29.12 being used as a forwarder?

Just want to remind everyone that with AD, we cannot use any ISP's DNS
servers in a machines' (DC or client) IP properties or many things can go
wrong. Just use the internal DNS and configure a forwarder for efficient
Internet resolution.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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 Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Gregg Hill]

Yes, the event ID is 5504. I do not see 206.13.29.12 in the server's IP
settings. I am not sure what you mean by it being used as a forwarder.

Gregg Hill




"Ace Fekay [MVP]"

 

[Ace Fekay [MVP]]

In

Yes, the event ID is 5504. I do not see 206.13.29.12 in the server's
IP settings. I am not sure what you mean by it being used as a
forwarder.

Gregg Hill

This error can either be an easy error or a tough one to fix. Usually htis
error means an underscrore or a space is in a computername somewhere. Can
you confirm that? It maybe trying to resolve the name outside, becaues it
doesn't know what to do with the illegal character. Hence, why I believe
your machines are configured with SBC's DNS addresses.

So we'll also need to know your DNS config on your client machines and DCs.
Hopefully, what we're looking for is that you are not using SBC's DNS
address in these machines' IP properties.

As for forwarding, that's configured in DNS properties, forwarding tab. Do
you have a forwarder configured?

Also, make sure Secure Cache against Pollutiuon is checked off in DNS
properties as well.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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 Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.