• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Bind, forward zones and wildcard entries

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Stratus_ss

Overclockix Snake Charming Senior, Alt OS Content
Joined
Jan 24, 2006
Location
South Dakota
So I have a problem that I don't know how to solve. This is my situation

Code:
              99.1          99.100
Client --> DNS --> subdomain DNS

I have a forward zone setup in the primary DNS that looks like this

Code:
zone "ose.mydomain.com" {
	type forward;
        forward only;
	forwarders { 192.168.99.100; };
};

This works when clients try to get to machines on ose.mydomain.com, however in ose.mydomain.com I have a wild card entry

Code:
*.apps.ose.mydomain.com   IN  A   192.168.200.61

If the client has their primary dns set to 192.168.99.100 the wild card lookup works. However if the client's primary DNS is set to 192.168.99.1 the forward/reverse lookups work EXCEPT for the wild card.

At one point I tried having a forward zone specifically for the subdomain

Code:
zone "apps.ose.mydomain.com" {
	type forward;
        forward only;
	forwarders { 192.168.99.100; };
};

But this didn't work. I am at a loss as to why neither of these approaches worked
 
I'm kind of surprised this hasn't gotten any responses... is what I am trying to do wrong or crazy in a general sense? Is it reasonable to expect this behaviour
 
Back