tag:blogger.com,1999:blog-3266263034124005485.post6331263771625054514..comments2024-03-24T23:19:30.504+00:00Comments on Fragmentation Needed: Cisco DHCP client bummerchris margethttp://www.blogger.com/profile/09716555871346949419noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3266263034124005485.post-20593248772415841422015-09-27T14:31:11.114+01:002015-09-27T14:31:11.114+01:00"By default IOS will only try to do a lookup ..."By default IOS will only try to do a lookup from interfaces in the global vrf."<br /><br />That's not correct. IOS has "VRF Aware DNS", which (aside from this issue) does the right thing: Lookups get done against the correct server depending on the VRF context of the query.<br /><br />Forcing the VRF to use the correct server (ip name-server vrf x.x.x.x) works, but it presumes that I know beforehand what server is available for me to use. In this case, I do not know where the DNS server is. I need to learn it from DHCP.chris margethttps://www.blogger.com/profile/06646973209424821070noreply@blogger.comtag:blogger.com,1999:blog-3266263034124005485.post-45679472161277044722015-09-27T08:52:13.370+01:002015-09-27T08:52:13.370+01:00Hello,
Have you tried using the ip domain lookup s...Hello,<br />Have you tried using the ip domain lookup source-interface fa4 command?<br />By default IOS will only try to do a lookup from interfaces in the global vrf.<br /><br />The question for me is whether or not IOS will install the DHCP DNS and perform the lookup with that server, which is something I can't lab at the moment. You can force the name server by using up name-server vrf and see if that works before trying put dhcp.<br />Good luck.<br /><br />Anonymoushttps://www.blogger.com/profile/04883487008988760145noreply@blogger.com