These were both welcome improvements, but there were still three issues remaining that make the USG DNS less than useful:
Removed 'host-decl-name' from registration consideration, so hosts with DHCP reservations defined in the controller will have the client-provided client hostname registered. DHCP client hostname DNS registration improvements - strip invalid characters and register the remaining, and allow periods. Firmware 5.4.16 also, finally, allowed us to actually register hosts where we had specified an IP Reservation (previously these hosts would not be registered at all).įrom Ubiquiti’s release notes for 5.4.16:
Prior versions to Firmware 5.4.16 didn’t have this update and just gleefully registered names with invalid characters (which then couldn’t ever be used to resolve the host). a space) and replace them with a hyphen (-). The only modification that the USG makes (as of Controller firmware version 5.4.16) is to strip invalid DNS characters (e.g. You can log into your USG via SSH then cat /etc/hosts to see the table.
That Client Identifier is then inserted into the /etc/hosts table on the USG when requested via DHCP.
my Apple TV in the Guest Room is named “Guest Room”).
Both Sonos Play:1’s and Play:5’s will register as “SonosZP”)), or it may be user-configurable on the device itself (e.g. That Identifier might be factory-set by the manufacturer (like in the SmartThings and Sonos examples below (e.g. When your client requests a DHCP address from the USG, that request includes a Client Identifier. As of this writing, there is currently no way in the GUI to create a static DNS entry. That means that it won’t appear in the DNS resolution “table” on the USG at all, because it never retrieved its IP via DHCP.
Unfortunately, when you bond the two NICs the Synology only supports a Manual IP assignment. I have a Synology NAS and that NAS supports bonding of the two LAN interfaces to give me 2Gbps of throughput to the NAS. There is also the issue of static DNS hosts. As of this writing, there is currently no way in the GUI to update a DNS entry for a DHCP client. Also, these Client Identifiers can often not be changed on the client, meaning you’ll be stuck always using them for resolution. st-D052BC263C7B0001, which is my SmartThings Hub). The issue you’ll face with a moderately complex network (or any network in which you have servers you wish to access) is that you won’t know what names they register with in the USG DNS, and even if you do (by checking the Clients tab on the Controller), you won’t be able to remember them (e.g. However, this is purely cosmetic and the Alias will only be visible in your Clients listing on the Controller (and in reports, analysis, insights, etc.). You can override the default Client Identifier name for a given client by creating an Alias for it: This is why you’ll see “garbage” on your Clients list like these: The Client Identifier is how the USG records the name of your various systems on the internal network, which are populated in the Clients tab on your Controller. In fact, it provides only one type of DNS registration: Dynamic host name registration based on the Client Identifier coming from the DHCP request. The problem is that the USG provides only very rudimentary DNS services for your internal network.