kevin. the whole/partial reason for all of this. the local system with the dhcp, doesn't have a dns!!! you come in the lab, connect, you get your ip. as to the external world, the dhcp serves the dns for the rest of the world. as to the internal boxes, you get an ip, nothing more!! it wasn't the intent to have boxes hooked up for long... we're bending the system... so to do that, we'd rather not have to always recall ipaddresses, so we're going to kludge this.. On Tue, Jan 21, 2014 at 11:37 AM, Kevin Martin <ktmdms@xxxxxxxxx> wrote: > On 01/21/2014 10:36 AM, Kevin Martin wrote: >> On 01/21/2014 09:54 AM, bruce wrote: >>> tim.. >>> >>> i have complete control over the local dns >>> >>> the local client machines are given hostnames upon creation/boot up.. >>> >>> the idea is to be able to have someone within the local network, >>> who'[s machine has been configured to point to the local dns, to be >>> able to use the boxname "foo" to get to the machine instead of the >>> ipaddress of the "foo" box. >>> >>> normally,, all of this would be handled by thre dhcp server.. in this >>> case it isn't. >>> >>> so you need to do a kludge which involves updating the local dns >>> server/records with the updated mapped ip/name. >>> >>> >>> >>> On Tue, Jan 21, 2014 at 10:49 AM, Tim <ignored_mailbox@xxxxxxxxxxxx> wrote: >>>> Allegedly, on or about 21 January 2014, bruce sent: >>>>> some of us who deall with getting dhcp ipp addresses, don't have >>>>> access to managing the dhcp server!!! >>>> >>>> And you have access to a DNS server that you can reprogram?? >>>> >>>> If so, then have a look at the already existing coding for the DHCP >>>> servers, and apply the same with your client. >>>> >>>> -- >>>> [tim@localhost ~]$ uname -rsvp >>>> Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 >>>> >>>> All mail to my mailbox is automatically deleted, there is no point >>>> trying to privately email me, I will only read messages posted to the >>>> public lists. >>>> >>>> George Orwell's '1984' was supposed to be a warning against tyranny, not >>>> a set of instructions for supposedly democratic governments. >>>> >>>> >>>> >>>> -- >>>> users mailing list >>>> users@xxxxxxxxxxxxxxxxxxxxxxx >>>> To unsubscribe or change subscription options: >>>> https://admin.fedoraproject.org/mailman/listinfo/users >>>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >>>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >>>> Have a question? Ask away: http://ask.fedoraproject.org >> can you 'dig @primaryDNS your.domain.com axfr' the primary DNS server? If you can't you probably won't be able to do what you are >> hoping to achieve as the primary name server isn't allowing you to do a zone transfer. You would essentially have to know each and >> every host and do a name lookup of each and every host one at a time and capture that information and build your zone(s) that way. >> >> Kevin >> > better yet, why don't you just point the dns clients to the primary dns server, set the domain to search, and do the name resolution > that way? > > Kevin > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
