DNS WIldcard resolving " * " literally

[10base2]

Native Microsoft DNS on Windows 2000 SP2. Name servers run DHCP and WINS too. Nothing else.

Here's the situation: the wildcard entry has been created, but when I check variations of the real hostname with nslookup the server returns an authoritative reply but no address. If I do a lookup for the wildcard entry itself " * ", it actually resolves to the correct wildcard IP address. In other words, the asterisk is being seen as a literal character instead of a wildcard: *.subdomain.domain.edu resolves, but anything.subdomain.domain.edu does not. Here's where it gets wierd: my secondary DNS server resolves it just fine. The only way it can get to my secondary server is to be replicated from the primary where I set up the wildcard!
If I did it wrong, it shouldn't work at all! ACK!!!

Any ideas where I can look to solve this? Should I turn to Microsoft support for help? I'm at the limit of my skills.

 

[10base2]

Oops...typo... Servers have >sp4< not sp2.

 

[GlenJohnson]

Try using nslookup from

http://www.samspade.org

and see what happens. Might not be your setup at all.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

TTinChicago

http://www.johnsoncomputers.us

 

[Whoheard]

Look for an extra blank space or missing period in the entry of the configured wildcard entry.


bob

I know what I know and that's all I know. What I don't know I'll find out.

 

[10base2]

My secondary DNS server works and it gets all of the zone info directly from the primary- the server that has the problem. Could it still be a typo if the secondary dns server is resolving correctly?