So for example dig shows:

```
Z:\Backup> dig pa.example.com

; <<>> DiG 9.16.8 <<>> pa.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11731
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;pa.example.com.     IN      A

;; ANSWER SECTION:
pa.example.com. 59   IN      A       192.168.0.223

;; Query time: 20 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 12 19:47:46 Pacific Daylight Time 2023
;; MSG SIZE  rcvd: 70
```

(Which points to the correct local ip).

If i just go to 192.168.0.223 in chrome/curl/etc, it works fine, but if i do the same on pa.example.com i get:

```
Z:\Backup>curl -vvv http://pa.example.com
*   Trying 192.168.0.223:80...
* Connected to pa.example.com (192.168.0.223) port 80 (#0)
> GET / HTTP/1.1
> Host: pa.example.com
> User-Agent: curl/7.83.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Content-Type: text/plain
< Location: http://PurpleAir-f63d.lan/redirect
< Pragma: no-cache
< Cache-Control: no-cache
< Content-Length: 0
< Connection: close
<
* Closing connection 0
```