DSL/DNS Confusion

Kevin Darcy kcd at daimlerchrysler.com
Fri Feb 25 23:01:04 UTC 2005


You're not leaving those angle brackets (<>) in there, are you?

- Kevin

Flash Love wrote:

>Flash Love wrote:
>
>  
>
>>Barry Margolin wrote:
>>
>>    
>>
>[snip]
>
>  
>
>>>>And, how to correctly configure the domains: benu/blackdiamond.widge.org
>>>>and rescue911design.com to use the dynamically assigned ip on eth1.
>>>>Presently, I have simply entered the external ip address in the
>>>>benu/blackdiamon.widge.org and rescue911design.com zone files.
>>>>        
>>>>
>>>You can use the dynamic update protocol of DNS.  See the "nsupdate"
>>>command.
>>>      
>>>
>
>When using the example below from
>http://ops.ietf.org/dns/dynupd/secure-ddns-howto.html it produces the
>following error message. I have used vi w/ set list in the
>dhclient-exit-hooks file and found only UNIX lf and no whitespaces. Also, I
>have used qd.ip.of.ns. as 127.0.0.1 and the text ns w/trailing dot in the
>SERVER parameter both produces the same results. What else is needed to
>resolve this complaint?  
>
>=================================
>/var/log/messages
>=================================
>Feb 25 16:12:36 roxie ifup: /etc/dhclient-exit-hooks: line 2: syntax error
>near unexpected token `newline'
>Feb 25 16:12:36 roxie ifup: /etc/dhclient-exit-hooks: line 2:
>`SERVER=<ns1.benu.widge.org.>'
>
>==============================
>Example from Secure DDNS Howto
>==============================
>TTL=3600
>SERVER=<qd.ip.of.ns>
>ZONE=<zone-fqdn>
>HOSTNAME=<fully-qualified-client-hostname>
>KEYFILE=<generated-keyfile>
>        
>nsupdate -v -k $KEYFILE > /dev/null << EOF
>server $SERVER
>zone $ZONE
>update delete $HOSTNAME A
>update add $HOSTNAME $TTL A $new_ip_address
>send
>EOF
>
>Flash
>
>  
>
>>>>My goal is to set up:
>>>>
>>>>Home lan = blkdiamonds.lan w/ 192.168.2/24 (eth0)
>>>>Web = benu.widge.org w/ dynamic ip (eth1)
>>>>Web = blackdiamond.widge.org w/ dynamic ip (eth1)
>>>>Web = rescue911design.com w/dynamic ip (eth1)
>>>>
>>>>        
>>>>
>[snip]
>
>
>
>
>
>  
>




More information about the bind-users mailing list