Core Web App

#1 Can create overlapping IPs with top level network and subnets. Create network: 192.168.15.0/24 Create subnet: 192.168.15.64/28 Assign IP to subnet: 192.168.15.65 Assign IP to network: 192.168.15.65 No verification that it is in use. #2 Can assign Network IP to Device - Should not be allowed #3 Can assign Broadcast IP to Device - I question this as well... Cannot search for IP within a network (primary network), must select subnets manually

It would be great if custom DNS entries can be tracked (e.g. custom cname/A/AAAA etc. records) In addition, the ability to store historic information/change tracking in order to easily tell dates at which key information changed. (Bonus points if this checking can happen more often or on a custom schedule and linked to alerting!)

Would be great if we had the ability to Snapshot the results from the automatic DNS whois. If the client updates a MX or A record we could see what it was vs what it was. Especially useful for when the client give the public dns login to a web developer who decides to make changes without consulting IT. Ideally would be great to have a timeline with the following versions; 1Yr - 6 Months - 3 Months -1 Month - 2 Weeks - 72 Hours - 24 Hours

Currently, child network IP usage does not count towards a parent network's IP usage. Please change this so that IP usage in a child network is reflected in the parent network as well.

Ability to import CSV/TXT Zone dump. Linking records to SSL certs websites are an added bonus.

with the coming changes to tls expiry it would be nice to be able automate renewal without having to leave ports open or having to do it manually every month.

I would like to be able to set a list to be used for the IP address status field, like it is possible to do for the Network Status and Role fields. Being able to customize the IP address statuses would be really useful.

Have the website tool get the proper DNS A record for host/subdomain instead of the root domain. Currently the service pulls information from this cloud function: https://us-central1-flawless-helper-365917.cloudfunctions.net/website_lookup?name=host.domain.tld . No matter the host or subdomain, the returned A record is always for the root domain.

It would be a nice feature to be able to use different DNS servers for the “Website Monitoring” and the “DNS” records section. We have an internal DNS that is required in order to hit our hosted sites, but we want to see the “True” records from an external DNS in the documentation as well. (Maybe show both?)