How To Register Fqdn On A Dns Server
- Home
- Networking
- DNS
I have two Active Directory integrated DNS servers running on my network. I would like to figure out how to create a non FQDN record on my servers. What I mean by this is as follows.
If I create a DNS record in my domain forward Lookup zone "mydomain.ad" called "Test" and then do an nslookup for "test" from a non domain joined machine that lookup fails. because the record is actually "test.mydomain.ad" if I do an nslookup for "test.mydomain.ad" there is no issue.
I need the DNS record to be resolvable as simply "test" from a non domain joined machine or network equipment.
hopefully that makes sense :-)
Well, you can create a new forward lookup zone called unifi (or test, or whatever), and in that zone create a new A record with no host name but the ip address 10.10.10.116. That will create a fqdn of unifi.
Out of curiosity, have you sniffed what the DNS request is from the phones?
The help desk software for IT. Free.
Track users' IT needs, easily, and with only the features you need.
24 Replies
*edited* All DNS records are looked up FQDN style if you are not domain joined.
Also, if your DHCP scope supplies the "Connection Specific DNS Suffix" to the non joined workstations, and it matches the DNS domain you have the host in, it will also work without the FQDN.
Yes, but they are still FQDN because they are in the domain forward lookup zone. Windows devices seem able to figure this out but android and linux devices not so much.
The issue I am having is that I have a bunch of voip phones (android based) that are supposed to phone home to a (lunix based) management server. They do this by looking up a DNS record the manufacture sets in firmware. They all fail to lookup the dns record that points to the IP of the server. If I manually input the FQDN on every phone (pain in the butt) they resolve the dns record fine and show up on the management server, left to their own devices they all fail to resolve the dns name and find the server
Well what your asking is not a feature of DNS, it would have to be a feature of your devices or management software.
What is the DNS record the manufacturer sets up by default?
The DNS record is an A record called "unifi"
So let me understand one more part. It looks like using the FQDN is exactly what you should be doing on each device. Are you just trying to take a shortcut by making an A record for the default entry on each device's DNS hostname field? I understand why you might want to do that, but "test" is an awefully lame name for a production phone server DNS record you know?
This may be a problem with your DNS lookup tool. I know that when I do a ping, the command "ping test" will ping test.mydomain.com, but doing a DNS lookup with dig requires the fqdn.
The search domain is my AD domain, I will look to see if I can set a search domain via DHCP.Chad.w wrote:
Ok, I have an idea. If you attach a windows device to this same network and do an ipconfig from a command prompt, what does it say for your "Connection specific DNS suffix?" On my iPhone this same field is called "search domain" and in both cases this is populated by the DHCP server. If you can get that to be the same as the domain in your FQDN it will work. You do this in your DHCP scope settings.So let me understand one more part. It looks like using the FQDN is exactly what you should be doing on each device. Are you just trying to take a shortcut by making an A record for the default entry on each device's DNS hostname field? I understand why you might want to do that, but "test" is an awefully lame name for a production phone server DNS record you know?
By making the DNS entry for Unifi the devices are supposed to automatically locate the management server when powered on (even when in the default out of box unconfigured state) so that I can adopt and manage without having to get hands on and manually specify the server on every device. Since almost all of these devices are at remote sites this is an important feature to have working. Test isn't the server name. Just a record I created to test with that doesn't affect production equipment. Once I figure this out test gets deleted :-)
Edited Nov 11, 2016 at 03:43 UTC So on my DHCP server I already have option "015 DNS Domain Name" configured as my domain
I don't see any further options to specify a search domain
Do you have DHCP option 15 set to hand out your DNS suffix?
Why not use the IP instead of doing a DNS lookup ?
I will test Option 119 out on Monday, ThanksPatrickFarrell wrote:
I am guessing you didn't read all my posts in the thread, but using the IP has 2 big drawbacksJeffDeathKnight wrote:
Why not use the IP instead of doing a DNS lookup ?
- If I ever change the IP of the server for some reason I lose management of all my phones
- I have to manually enter the IP on all my phones which are across multiple locations. I am trying to get the auto call home to server feature working so I don't have to touch any phones manually
I don't know which tool you are using. I use "nslookup" from command prompt. Try it.
Looks like you are using Ubiquity products. I use some of their APs, as well as other products that discover their controller via DNS lookup of a predefined hostname. I can tell you that it works. Just be sure that your DHCP server hands out your DNS servers and your DNS domain name. Your A record in DNS should be for unifi.mydomain.ad .
Brand Representative for Vembu Technologies
You can put DNS suffix on workgroup computers with your AD fqdn say mydomain.ad. It should resolve the name "test" with AD joined computers and workgroup computers.
Yes, its Ubiquiti equipment. and yes, the DNS record works fine with their network gear. but the phones are Android based and even though it is supposed to work with the phones it isn't. the phones are not picking up the search domain and hence failing to lookup the A record. I have verified this.kevinmhsieh wrote:
I don't know which tool you are using. I use "nslookup" from command prompt. Try it.
Looks like you are using Ubiquity products. I use some of their APs, as well as other products that discover their controller via DNS lookup of a predefined hostname. I can tell you that it works. Just be sure that your DHCP server hands out your DNS servers and your DNS domain name. Your A record in DNS should be for unifi.mydomain.ad .
Well, you can create a new forward lookup zone called unifi (or test, or whatever), and in that zone create a new A record with no host name but the ip address 10.10.10.116. That will create a fqdn of unifi.
Out of curiosity, have you sniffed what the DNS request is from the phones?
No, Haven't tried to capture the traffic, I installed an app on the phone so I could do some DNS lookup testing (screen shots above) and I did some google searching and it seems there is a known issue with certain Android versions ignoring search domains that are provided by the DHCP server and then failing to be able to lookup local DNS records. I am starting to think this is the issue I am dealing with and that my DNS is actually fine.kevinmhsieh wrote:
Well, you can create a new forward lookup zone called unifi (or test, or whatever), and in that zone create a new A record with no host name but the ip address 10.10.10.116. That will create a fqdn of unifi.
Out of curiosity, have you sniffed what the DNS request is from the phones?
No, nothing technically wrong, however your suggestion has already been covered in detail above and didn't add anything newGopal (Vembu) wrote:
Moderator,My reply for this post is made to hidden. Could you explain me why ? . Anything wrong in my reply ?. Screenshot attached.
This suggestion worked. I created a zone called Unifi and the un-adopted phone popped right up on the controller.kevinmhsieh wrote:
Well, you can create a new forward lookup zone called unifi (or test, or whatever), and in that zone create a new A record with no host name but the ip address 10.10.10.116. That will create a fqdn of unifi.
Out of curiosity, have you sniffed what the DNS request is from the phones?
My research suggests as I mentioned above that there is a bug in certain versions of android whereby it ignores search domains and hence fails to use local dns records. I think this is the case with these devices.
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
How To Register Fqdn On A Dns Server
Source: https://community.spiceworks.com/topic/1916594-how-do-i-create-a-dns-record-that-isn-t-a-fqdn
Posted by: coheeconsor67.blogspot.com
0 Response to "How To Register Fqdn On A Dns Server"
Post a Comment