 |
| Prev-20 | Home | Next-20 |
| Prev-20 | Home | Next-20 |
| Prev- | Prev- | Bind- | Jun- | Next- | Next- |
| Subject: | Re: CNAME setup issue |
| Group: | Bind-users |
| From: | Tim Traver |
| Date: | 25 Jun 2007 |
I guess the real solution is to just set the A record for it, but that
means that if the destination ever changes their IP, that we will have
to make that change as well...
Tim.
Chris Buxton wrote:
> You're right, you can't have the name of the zone (the primary domain
> location, to use your words) be a CNAME alias.
>
> Use one or more A records (or other records, such as an MX record)
> instead. Or set up a web server that handles "http://domain2.com/xyz"
> and redirects it to "http://www.domain2.com/xyz", which is an alias of
> the desired outside name.
>
> Chris Buxton
> Men & Mice
>
> On Jun 25, 2007, at 3:15 PM, Tim Traver wrote:
>
>> Thanks Chris for your response,
>>
>> I have seen now in the logs that the zone doesn't even get loaded
>> with a CNAME and other data error...
>>
>> So, that's kind of confusing though...that basically means you can't
>> have the primary domain location as a CNAME ?
>>
>> If that is the desired effect, how would one go about it ???
>>
>> Thanks,
>>
>> Tim.
>>
>>
>> Chris Buxton wrote:
>>> You've made a classic mistake, violating the CNAME and other data rule.
>>>
>>> A CNAME record may not have the same name as any other record,
>>> including another CNAME record. (If you're using DNSSEC, you should
>>> already know enough to ignore the absolutism presented here.)
>>> Therefore, the following is always an error that will cause your
>>> entire zone to fail to load:
>>>
>>> @ SOA [... fill in values here ...]
>>> CNAME anything.at.all.
>>>
>>> On the other hand, this will not generate an error:
>>>
>>> @ SOA [... fill in values here ...]
>>> www CNAME anything.at.all.
>>>
>>> The upshot is, you need to delete that first CNAME record.
>>>
>>> Chris Buxton
>>> Men & Mice
>>>
>>> On Jun 25, 2007, at 2:54 PM, Tim Traver wrote:
>>>
>>>> Hi all,
>>>>
>>>> ok, this may be a simple question, but I've racked my brain over it
>>>> for
>>>> too long and can't figure it out...
>>>>
>>>> I have a DNS server set up to be an authoritative server only. It has
>>>> the following main configuration parameters :
>>>>
>>>> options {
>>>> directory "/etc/namedb";
>>>> recursion no;
>>>> interface-interval 30;
>>>> allow-transfer { any; };
>>>> dump-file "/var/dump/named_dump.db";
>>>> statistics-file "/var/log/named.stats";
>>>> query-source address * port 33701;
>>>> notify no;
>>>> };
>>>>
>>>> I have a zone file set up for a domain that looks like this (will use
>>>> the example of domain2.com):
>>>>
>>>> $TTL 4h
>>>> @ IN SOA ns3.domain1.com. postmaster.domain1.com. (
>>>> 2007062508 ; Serial
>>>> 3600 3600 1209600 3600); ;
>>>> Refresh,Retry,Expire,Min TTL
>>>>
>>>> IN NS ns3.domain1.com.
>>>> IN NS ns4.domain1.com.
>>>> ;- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>>>> domain2.com. IN CNAME ghs.google.com.
>>>> www IN CNAME ghs.google.com.
>>>>
>>>>
>>>> Problem is, that if I query the server directly, I get the following
>>>> answer :
>>>>
>>>> root@ns1# dig @ns3.simplenet.com mediabait.com
>>>>
>>>> ; <<>> DiG 9.3.1 <<>> @ns3.domain1.com domain2.com
>>>> ; (1 server found)
>>>> ;; global options: printcmd
>>>> ;; Got answer:
>>>> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 55721
>>>> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>>>>
>>>> ;; QUESTION SECTION:
>>>> ;domain2.com. IN A
>>>>
>>>> ;; Query time: 2 msec
>>>> ;; SERVER: 209.xxx.xx.x#53(209.xxx.xx.x)
>>>> ;; WHEN: Mon Jun 25 14:47:33 2007
>>>> ;; MSG SIZE rcvd: 31
>>>>
>>>> But, when I do a query on another domain that I know has a CNAME as
>>>> well, I get the following :
>>>>
>>>> ;store.domain3.com. IN A
>>>>
>>>> ;; ANSWER SECTION:
>>>> store.domain3.com. 14400 IN CNAME www.empirevstore.com.
>>>>
>>>> Does anyone see a problem with this setup ???
>>>>
>>>> Thanks,
>>>>
>>>> Tim.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
| Prev- | Prev- | Bind- | Jun- | Next- | Next- |