Changing output of bind

[Andy Shellam (Mailing Lists)]

Roland,

Please don't copy Marc in, this was a mistake on my part!  If he wanted 
to join in on DNS problems I'm sure he'd join the list! :)

Why, exactly, do you want to have a catch-all for all domains?  You 
could have a single zone file for all domains your DNS server is 
authoritative for, but if you want to re-direct all web lookups to a 
single IP, I think you'd be better looking at the networking side of 
things (ie. NATting all traffic on port 80 to 195.110.192.3)

I don't believe this is something Bind can easily do.

Andy.

Roland Zoder wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hm,
>
> i was told that this is exactly what it should not be.
> That's a wildcard host record for one domain;
> i want/need a wildcard for _all_ domains.
>
>
>   
>> I'm not sure how this ended up on nagios-users but it looks like the OP
>> might just need to create a wildcard DNS record --
>>
>> * 	IN	A 	195.110.192.3
>>
>> Any unknown host records would then resolve to that IP.
>>
>> --
>> Marc
>>
>>
>>     
>>> -----Original Message-----
>>> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
>>> bounces at lists.sourceforge.net] On Behalf Of Andy Shellam (Mailing
>>>       
>> Lists)
>>
>>     
>>> Sent: Monday, December 11, 2006 6:52 AM
>>> To: RZ; Nagios Users mailinglist
>>> Subject: Re: [Nagios-users] Changing output of bind
>>>
>>> From my experience as a programmer, if you don't know why you're
>>>       
>> doing
>>
>>     
>>> something, it's impossible to do it correctly.
>>>
>>> The example you've shown us is a zone file.
>>> It only returns the relevant part of the zone in answer to a query -
>>>       
>> so
>>
>>     
>>> if a user requests, "wwww.<the_domain>" they will get "wwww IN A
>>> 195.110.192.3" returned.
>>>
>>> I think what you've been asked to do is try and catch all spelling
>>> errors of a request, so if user types in "wwww.yourdomain.com" instead
>>> of "www.domain.com" they will get the correct record.
>>> This is a different thing to rewriting the named output, and the
>>>       
>> answer
>>
>>     
>>> lies in creating additional records for each "mistake" possibility in
>>> your zone file either through scripting or manual input.
>>>
>>> RZ wrote:
>>>
>>>       
>>>> Hi,
>>>>
>>>> i'm a dns newbie but a (medium experienced) c programmer.
>>>> I was told to change named output in that way that it will return
>>>> something like the following example (if i remember things right it
>>>> should give an authoritative answer for domains contained in a
>>>>         
>> file). I
>>
>>     
>>>> _thought_ it would not be too much an effort to change the named
>>>>         
>> output
>>
>>     
>>>> in an appropriate way - but at the moment i'm really lost.
>>>>
>>>> What the use of this ? - i honestly don't know.
>>>>
>>>>
>>>> ;      @(#)named.hosts,v 6.1 1993/08/25 16:51:44 stevea Exp -
>>>>         
>> STREAMware
>>
>>     
>>>> TCP/IP  source
>>>> ;      SCCS IDENTIFICATION
>>>> ;
>>>> ; BIOS
>>>> ;
>>>>
>>>> @		IN SOA	ns1.web.at.	hostmaster.biosnet.at. (
>>>> 			2006090101      ; Serial
>>>> 			28800   ; Refresh
>>>> 			7200	; Retry
>>>> 			604800  ; Expire
>>>> 			86400)	; Minimum
>>>> 		IN NS	ns1.web.at.
>>>> 		IN NS	ns2.web.at.
>>>> 		IN A    195.110.192.3
>>>>                IN   TXT   "v=spf1 -all"
>>>>
>>>> ;
>>>>
>>>> ;
>>>> ww                  IN   A	195.110.192.3
>>>> www                 IN   A	195.110.192.3
>>>> wwww                IN   A	195.110.192.3
>>>> www2                IN   A	195.110.192.3
>>>> ;
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>         
>>>>> It might help if you explain what you're trying to achieve by doing
>>>>>           
>>> this.
>>>
>>>       
>>>>> When a host requests "www.*" then it'll be given the appropriate
>>>>>           
>>> records
>>>
>>>       
>>>> >from your zone file.
>>>>
>>>>
>>>>         
>>>>> If a client requests a different host but gets "www" instead it'll
>>>>> confuse things.
>>>>>           
>>     
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFfa0QiFS0ynzRzi8RAswqAJ9dnBeKkwqAL5uSIyDQyJtPirVQngCffmg7
> ILhwjorxqh/eNxjq2Q10JK4=
> =pwnX
> -----END PGP SIGNATURE-----
>
>
>
> !DSPAM:37,457dae7f30862030120255!
>
>
>   


-- 
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834