FQDN DNS Setup for Avaya Publishing over WAN
Budget: $30 – $250 CAD
My Avaya IP Office is already reachable over the WAN through a static public address that’s been properly NAT-ed on our firewall. All that’s left is to bind that IP to a Fully Qualified Domain Name so users can reach the system by name instead of numbers.
The domain is already registered and managed through Cloudflare, and I have full access to the DNS dashboard. I simply need you to create the correct records (A, AAAA if needed, and any supporting SRV or CNAME entries Avaya might require), propagate them, and verify that the new hostname resolves globally to the public IP.
Once the records are live, please confirm with standard lookups—`dig`, `nslookup`, or your preferred tool—and send me the results so I can close the change request internally. This should be a quick task for someone comfortable with Cloudflare’s panel and basic DNS troubleshooting.
The domain is already registered and managed through Cloudflare, and I have full access to the DNS dashboard. I simply need you to create the correct records (A, AAAA if needed, and any supporting SRV or CNAME entries Avaya might require), propagate them, and verify that the new hostname resolves globally to the public IP.
Once the records are live, please confirm with standard lookups—`dig`, `nslookup`, or your preferred tool—and send me the results so I can close the change request internally. This should be a quick task for someone comfortable with Cloudflare’s panel and basic DNS troubleshooting.