Search Again:

Re: Wildcards?

From: Paul Didzerekis
Date: Thursday, January 13, 2000
Time: 12:24:00 am

>At 8:32 AM -0800 1/12/2000, Sam Lewis wrote:
>>I've seen one mention of wildcards in the QuickDNS manual but no
>>further explanation.
>>
>>Can QuickDNS be setup so that there are known addresses and then a
>>wildcard address so that any unknown address is sent to the wildcard
>>address? For example, a simple domain file:
>>
>>
>>samlewis.com ns ns.samlewis.com
>>samlewis.com mx 10 mail.samlewis.com
>>www.samlewis.com A 192.168.0.1
>>*.samlewis.com A 192.168.0.2
>>
>>
>>So that the domain acts normally for all "known" or defined
>>addresses but say a request for "xyz.samlewis.com" comes in. Since
>>it is unknown but a wildcard is setup it is directed to 192.168.0.2?
>>
>>Is this correct or possible?
>
>That is indeed how it works; "*.samlewis.com" will match "bogus.samlewis.com", but it will not match "www.samlewis.com", nor will it match "samlewis.com".
>
>Note that this can also be used for MX records.
>
>One thing to note is a configuration that, on first glance, looks like it should work, but in fact does not:
>
>*.example.com. MX 10 mail.example.com.
>users.example.com. A 192.168.0.1
>mail.example.com. A 192.168.0.5
>
>If mail is sent to "user@users.example.com", it will be delivered to "users.example.com", not "mail.example.com". This is because the wildcard MX record doesn't match "users" - "users.example.com" is already a defined name, with an A record. The fact that it doesn't have an MX record is immaterial.
>
>So to put it in terms of what *does* work: A wildcard record will match any name that doesn't have any other record of any kind.
>____________________________________________________________________
>Chris Buxton cbuxton@menandmice.com
>Men & Mice http://www.menandmice.com
>Makers of: QuickDNS Pro



Messages In This Thread:



Return to Digital Point Solutions' Home Page