Jump to content

nsvora

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nsvora

  • Rank
    Noob
  1. Hi, I am using BIND 9.2.4 on LINUX 2.6.9. I am facing the following issue: The domain name is set to testdns.com and when i update my host name as test, the update goes through fine to the DDNS server. But when my host name reaches 64 characters, the server sends the "Format Error" response code. I know domain name can be upto 256 bytes, but is 63 limiting factor for the host name? Any help is appreciated. Thanks in advance, nsvora
  2. Hi anyweb, Thanks for the reply. My setup details are as below: There is Linux machine , DHCP server and DDNS server on a network. Currently , if the machine has achieved the IP Address from the DHCP server, its information is also updated in the DDNS server. My question was: If DHCP is disabled on the above machine, and IP Address is statically configured, should this information be updated in the DDNS server? - nsvora
  3. Hi All, I have a Linux machine having static IP configuration ( without DHCP). And if this configuration is changed, should this information be updated in the DNS server? In short, does Dynamic DNS make sense with static IP configuration? Any comment in this regard is highly appreciated. With Regards, nsv
  4. Hi All, While testing the DDNS server configuration with proprietory DHCP and DDNS client, I noticed a strange thing. Any help here is appreciated. Pre-condition: ---------------- DHCP and DDNS server are running on a single LINUX machine having following version: Linux ns1.testdns.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686 i686 i386 GNU/Linux The DHCP server was able to generate the dynamic IP Address as specified in the dhcpd.conf. DDNS server was able to add the entries in the forward and reverse zone files eg : testdns.com and 1.168.192.in-addr.arpa This ensures that DHCP and DDNS server settings are correct. Test Condition: --------------- I modified the client host name and restarted the named service so that changes are reflected in the zone files. The forward zone file was expected to be updated with the modified host name. Results: ---------- Forward zone had two entries viz; one with old host name and other with new host name. Analysis: ------------ I have found that this is happening because in DDNS client code, before updating the server database with modified host name, we are checking whether a record with
×
×
  • Create New...