Archives for dns

When Web Developers Take Control of Domains and Walk Away

Three times this week, I’ve encountered the same problem: web developers taking control of a customer’s domain and DNS, then leaving the customer without the support they need.

It’s frustrating to encounter as an IT technician. For the business owner trying to keep things running, it can be far worse.

A business puts its trust in someone to handle the technical side. The provider takes over the accounts, makes the changes and becomes the person everyone depends on. If that provider then becomes unavailable or stops helping, the customer can be left struggling to regain control of essential business services.

In my opinion, anyone taking on that level of control needs to take the responsibility seriously.

Your domain affects more than your website

Your domain is part of your business identity. It appears in your email addresses, on your invoices and across your advertising.

DNS contains the records that help connect that domain to services such as your website and email. Changes to those records can affect whether those services work. Microsoft specifically warns that incorrect DNS records can cause email and service outages.

That makes domain and DNS management a serious responsibility.

When access and documentation are missing, another IT technician may have to spend time identifying providers, tracing accounts and chasing permissions before they can address the original problem.

The customer ends up paying for the confusion through extra support costs, delays and disruption.

Taking control comes with responsibility

A capable web developer can manage domains, hosting and related services well. The arrangement needs clear boundaries and accountability.

If you manage these services for a customer, they should understand what you manage, what they are paying for, how to obtain support and what happens if the relationship ends.

A one-off website build and an ongoing support agreement have different scopes. Those differences should be explained upfront. A customer should never have to discover the limits of an arrangement during an outage.

If you are moving on, closing the business or no longer providing a service, organise a proper handover. Make sure the customer has the information and access needed to appoint someone else.

Leaving a customer dependent on accounts only you can access, while becoming unavailable to help, is unacceptable in my view.

The business needs to retain control

Business owners should have a secure, documented way to access or recover control of their essential services.

For Australian .au domains, check who is recorded as the registrant—the domain licence holder. auDA’s rules require an agent registering a domain on someone else’s behalf to record that person as the registrant. Having a developer arrange the registration should still leave the correct customer recorded as the licence holder.

Access also needs to be checked service by service. Domain registration, DNS hosting, website hosting and Microsoft 365 administration can involve different accounts and permissions. Access to the domain account does not automatically provide administrator access to Microsoft 365. Microsoft’s setup process treats those as separate requirements.

“The web people handle it” leaves too much unanswered.

The business needs to know who handles each service and how it can authorise another technician to help when necessary.

Five questions every business owner should ask

You should be able to get clear answers to these:

  • Where is our domain registered, and who is the registered licence holder?
  • Who manages our DNS, website hosting and email services?
  • How does our business securely access or recover the relevant accounts, including authentication and recovery methods?
  • Who is responsible for renewals, and what support does our agreement include?
  • What is the handover process if we change providers or our current provider becomes unavailable?

Keep those answers somewhere your business can access. Ask for them while everything is working.

You can leave the technical work to qualified people while still retaining control and understanding the arrangement.

Customers deserve clarity and a workable exit

My view is that a good provider should make a customer’s business easier to manage. That includes keeping records, explaining responsibilities and cooperating with other technicians when the customer needs help.

Customers should feel confident that they can get support, recover access and change providers without their business being left in limbo.

That is the standard I believe our industry should work towards.

If you are unsure who controls your domain, DNS or business email, BOSS IT Solutions can help you review the setup, identify gaps in access and documentation, and work out what needs to happen next.

Your business should retain control of the services it depends on.

Microsoft 365, Google Workspace and DNS Audit

Investigated two business domains using a mixture of Microsoft 365, Google Workspace and different DNS providers. One business had already been migrated to Microsoft 365 but still contained legacy Google verification, DKIM and SPF records that require further checking before removal.

The second business still relies on Google Workspace for email, but its DNS is controlled through a separate hosting environment rather than the normal domain management account. Reviewed current Google Workspace billing and identified a potentially redundant subscription and an additional licence that may no longer be required.

Estimated potential savings are approximately $32.67 per month, subject to Google’s billing commitments and confirmation that no important data or services still depend on the accounts. No DNS records, subscriptions or licences were removed during the investigation. Further work will include recovering administrator access, checking stored Google data, identifying the DNS administrator and reviewing Microsoft 365 security.

DNSSEC and Cloudflare DNS Configuration Repair

Investigated a website that was inaccessible through Google Public DNS despite appearing to work on some networks. The domain had previously been moved between DNS providers and was using a mixture of Cloudflare and another DNS service, resulting in conflicting DNS and DNSSEC configuration. Reviewed the nameserver delegation, DNS records and DNSSEC settings, corrected the configuration and removed the conflicting setup. Verified that the domain and website were resolving correctly again through public DNS services including Google 8.8.8.8.

Microsoft 365 Email Delivery and DNS Troubleshooting

Investigated Microsoft 365 email delivery problems across multiple accounts and computers. Exchange Online mail flow, tenant configuration and DNS records were reviewed, test messages were performed and additional email security records were added to DNS.

Microsoft 365 Exchange Email Migration

Prepared and completed an email migration to Microsoft 365 Exchange, including a PST backup, DNS changes and mail-flow testing. A new Outlook profile and Microsoft Authenticator were configured, and more than 16GB of existing email was imported into the new mailbox.

Google Workspace, IMAP and Microsoft Domain Troubleshooting

Resolved Google Workspace mail issues by creating an application password and setting up a clean IMAP-only Outlook profile. Work also continued on a Microsoft tenant problem, including adding a DNS TXT record to prove domain ownership and planning a possible future move to Exchange.

DomainHost to Cloudflare MS365 Migration Fixing WordPress SMTP Forms with Azure

Part 1 – DNS moved. Microsoft 365 mail flowing. SMTP working through Azure. Forms fixed. Mail online.

You Know How to Save Hundreds on Your Hosting, Right? Here’s How We Cracked It with Cloudflare

At Boss IT, one of the thing we do is help businesses and homeowners like you navigate the confusing world of web hosting, security, and website performance.

One of the most powerful tools we use is Cloudflare and its completely free and here’s why you should consider it:

What Cloudflare Does for You


  1. Faster Website:
    Cloudflare makes your website load faster by storing content in different locations around the world. That means happier visitors who stick around longer.



  2. Free SSL (Security):
    Cloudflare secures your website with a free SSL certificate. This means your website is safe for visitors, without paying for expensive certificates.



  3. Better Security:
    Cloudflare protects your website from hackers and bots. It’s like a security guard for your site, keeping it safe without extra cost.



Full Technical Rundown of Today’s IT Work (Including Domain Redirect and DNS Issues)

At Boss IT, we’ve been working on streamlining web infrastructure by migrating DNS services and ensuring website is faster and more secure. Here’s a breakdown of what was done today, including the com.au to net.au redirect, DNS migration, and the PowerShell script used for validation, as well as the pending Exchange email setup:


Domain Redirect (com.au to net.au)

  1. Domain Setup:


    • Two domains: com.au (used solely for branding purposes) and net.au (the primary domain).



    • The goal is to redirect all traffic from com.au to net.au, so visitors are automatically sent to the main website.


  2. Redirect Configuration:


    • We migrated DNS management for com.au to Cloudflare and set up 301 redirects for com.au to net.au using Cloudflare’s page rules.



    • Since com.au didn’t have a website or email services*, the redirect is primarily for branding, ensuring that any traffic or links to com.au are automatically directed to net.au.


  3. Challenges with Missing A/AAAA Records:


    • We encountered an issue because com.au didn’t have any A or AAAA records, obviously*, and these are required for Cloudflare’s proxying service to route the traffic correctly.



    • To resolve this, we used wildcard DNS records (*.com.au) to ensure that all traffic for com.au is routed through Cloudflare and properly redirected to net.au.



Cloudflare DNS and SSL Configuration for com.au

  1. DNS Migration to Cloudflare:


    • We successfully migrated the DNS management for com.au to Cloudflare, centralizing control and improving website performance.



    • DNS records were updated to direct com.au traffic to net.au, and all traffic was routed via Cloudflare’s network for enhanced speed and security.


  2. SSL Setup for com.au:


    • We enabled free SSL certificates via Cloudflare for com.au, ensuring that website traffic is secure with HTTPS encryption.



    • Always Use HTTPS was configured to automatically redirect all HTTP traffic to the HTTPS version.


  3. Security Configuration for com.au:


    • Cloudflare’s DDoS protection and firewall rules were implemented to secure com.au and ensure it stays protected from malicious traffic.



PowerShell Script for DNS Validation (We obviously used https://dnschecker.org as well, but code is more fun)

  1. PowerShell DNS Validation:



    • We used a PowerShell script to validate the DNS records and ensure the DNS propagation was happening correctly.




    • The script specifically checked for:




      • NS records: To confirm that Cloudflare’s nameservers were properly set up.




      • A records: To ensure Cloudflare was correctly routing traffic to the website.




      • MX records: To check if email traffic was correctly routed to the Exchange server.





    Example PowerShell Command:


    # PowerShell command to check NS records for com.au and net.au

    nslookup -type=ns com.au

    nslookup -type=ns net.au

    Untitled

    • The script confirmed that Cloudflare’s nameservers were active for both domains, and it will help us track DNS propagation for the NET.AU Domain when we migrate that across later.



Exchange Email Setup and DNS Migration for net.au (Pending)


  1. Repeat the Process for net.au:
    The steps we followed for com.au will need to be repeated for net.au. However, since net.au has live services such as Exchange (email) and an active website hosted, we need to be extra cautious to ensure everything continues to function correctly.


  2. Exchange Email Setup:


    • MX records will need to be updated for net.au, but we’ll keep the Exchange service hosted by the domain provider, as they host the Exchange Premium service. So essentially pointing back at them.



    • As with com.au, we’ll update the MX records in Cloudflare to reflect the correct Exchange settings. Since net.au uses Exchange, we’ll avoid disrupting the live email service by carefully updating the MX records at off-peak hours.


  3. Website and SSL:


    • net.au has an active website (currently hosted), so it will remain on WordPress cPanel hosting, but we’ll be managing DNS and SSL for net.au through Cloudflare.



    • We’ll ensure free SSL certificates are set up in Cloudflare for net.au so that the website remains secure with HTTPS encryption, even though it is still hosted on CD.


  4. Pending Tasks for net.au:


    • DNS migration for net.au will follow the same steps as com.au, but with extra care due to live services. We will use wildcard DNS records for the domain and Cloudflare’s proxying services to manage DNS and SSL while keeping Exchange and the website intact on Domain Host.



    • After the MX records are updated and DNS is fully propagated, we will test email routing and confirm that the website continues to operate as expected.